Settings - Symbols

External module paths - A semicolon (;) separated list containing either directory paths or file names. If a call stack entry belongs to a module that matches a file name from this list or a module that is located in a directory path from this list, then that call stack entry will be from an external module.

Tag as ignore, allocations with call stacks that contain these functions - A semicolon (;) separated list of function names. A function name can be either in the format of an exclamation mark (!) separated module name and function name (eg. oleaut32.dll!InitAppData) or just a function name (eg. InitAppData). Any allocation in a snapshot whose call stack contains an entry which matches any item in this list will be tagged as ignore. In a case where the function name specified may be either mangled or demangled, always specify the manged name. Do not specify an offset in the function.

Display source files - Enable to allow the displaying of a source code file in the user interface when a user selects an entry in the call stack.

Query source files - Enable to allow WonderLeak read source code files and test for the presence of an ignore line comment tag.

Source file local search paths - Some symbols (Such as TD32) may only provide relative source file paths as opposed to absolute file paths. If this happens you will need to manually specify one or more directory paths to allow WonderLeak resolve a relative source file path to an absolute source file path, allowing the source file to be read from disk and displayed in the user interface. The search paths are semicolon (;) separated.

Use _NT_SYMBOL_PATH - When resolving symbols in the PDB format the _NT_SYMBOL_PATH environment variable can be queried to instruct symbol resolution of the location of the remote symbol servers and local symbol file caches to use. Disable this option if you want to manually specify a custom symbol search path for PDB symbols.

Custom symbol path - If 'Use _NT_SYMBOL_PATH' is disabled you may manually specify a PDB symbol search path to use.

Use source server (if available) - PDB symbol resolution may require source server support in order to retrieve the correct source code files from a remote source server.

Source server cache path - The location to store any downloaded source code files from a remote source code server.